Systems and methods for performing a purchase transaction using rewards points

ABSTRACT

A system and method for performing a purchase transaction using rewards points by receiving a purchase request using a financial account with associated account information, determining based on the account information that the financial account is associated with a rewards program with rewards points, and providing the option to pay for the purchase using the financial account or at least a portion of the rewards points. The purchase may be paid for using rewards points from multiple rewards programs and/or multiple financial accounts.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority under 35U.S.C. § 120 to, U.S. patent application Ser. No. 15/949,417, filed Apr.10, 2018, which is a continuation of U.S. patent application Ser. No.12/106,074, filed Apr. 18, 2008, now U.S. Pat. No. 9,972,047, the entirecontents of which are fully incorporated herein by reference.

FIELD OF THE INVENTION

The present inventions relate to systems and methods for purchases usingrewards points.

BACKGROUND OF THE INVENTION

Numerous financial institutions and other entities offer membershiprewards programs whereby participants may receive “points” forperforming various actions, such as purchasing goods and services from aparticular merchant or using a particular transaction card. Customersoften, however, accumulate rewards points in multiple rewards programsthat they may be unable or unwilling to redeem in the ways required bythe provider. For example, an airline carrier offering a rewards programmay require that a large number of frequent flyer miles be accruedbefore the participant can earn a free flight. Customers also oftenaccumulate a small number of rewards points distributed across manydifferent rewards programs, which are not readily redeemable. Thesecustomers may lack a way to use their rewards points as currency and tocombine rewards points from multiple programs with cash from theirvarious accounts.

These and other drawbacks exist with current systems.

SUMMARY OF THE INVENTION

Various exemplary embodiments provide for performing a purchasetransaction using rewards points.

Many customers have accounts that they use to conduct financialtransactions in various ways. Online credit card purchases are just onewell-known example. It is also well-known that financial institutions,merchants, and other entities regularly offer membership rewardsprograms to their customers whereby customers can accumulate points inthe rewards program by purchasing items over time. For instance, acredit card provider may give its customers a certain number of pointsor frequent flyer miles for every purchase they make using their creditcards. Such rewards points, however, may only be redeemed in certaincircumstances according to terms set by the provider. For example, thecustomer may need to accumulate a large amount of rewards points or maybe limited to just certain rewards offered by the provider. It wouldtherefore be very beneficial if customers could simply use their rewardspoints as currency to purchase any items that they choose.

In one illustrative example, a customer may request a particularpurchase and provide account information to pay for the transaction,such as a credit card number. Based on the provided information, themerchant may determine that the customer belongs to a certain rewardsprogram. For example, the customer may have accumulated a certain numberof points that, when converted to their cash equivalent, would cover thevalue of the purchase. To find out whether the customer has a rewardsprogram, the computer system may request and receive information fromthe provider of the program or another entity. It may also retrieve suchinformation internally. If the computer system determines that thecustomer has a rewards program with rewards points available, it maythen present the customer with the option to pay for the purchase withthe rewards points rather than the account that was provided. Then, ifthe customer selects the option to pay with the rewards points, themerchant computer system may notify the provider, provide the purchaseditem to the customer, and later receive payment for the value of therewards points that were redeemed.

In another illustrative example, the computer system may storeinformation for the customer ahead of time so that the customer does notneed to input information with the purchase request. For example, acustomer may pre-register his or her credit card numbers and rewardsprograms with a merchant computer system. When the customer laterdesires to make a purchase, the merchant computer system may present theoption of paying with the preregistered rewards points or accounts.

In another illustrative example, the merchant computer system mayprovide the customer with the option to “split” the purchase price of anitem and buy it using rewards points from multiple programs, cash frommultiple accounts, or combinations of both. For example, if the price ofan item is $50, the customer may choose to pay for the item with 100points corresponding to $10, 2500 frequent flyer miles corresponding to$25, and $15 cash from a credit card. The merchant computer system mayperform various calculations to convert between rewards points and cashvalues. The merchant computer system may also communicate with variousrewards program providers and account providers to ensure the correctflow of payments.

In another illustrative example, the merchant computer system mayprovide an interactive user interface for the customer to choose amongvarious rewards points and/or accounts. The user interface may comprisevarious allocations that dynamically change in response to input fromthe customer. For example, if the customer increases the number ofrewards points from a particular program, the number of rewards pointsfrom another program may correspondingly decrease. In that way, thecustomer may make a more informed decision about how to spend his or herrewards points and cash.

In another illustrative example, an aggregator computer system may storeinformation for the customer's various rewards programs and accounts andthe merchant computer system may communicate with that system to providethe option to the customer.

In another illustrative example, a rewards program may be provided by anaccount provider and the merchant computer system may communicate withthe account provider using well-known authorization and settlementprocedures. For example, a merchant processor and card association mayrelay communications between the two systems.

Other embodiments are also within the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention, together with further objects and advantages, maybest be understood by reference to the following description taken inconjunction with the accompanying drawings, in the several Figures ofwhich like reference numerals identify like elements, and in which:

FIG. 1 depicts an exemplary system for performing a purchase transactionusing rewards points according to various embodiments of the disclosure;

FIG. 2 depicts an exemplary merchant computer system according tovarious embodiments of the disclosure;

FIG. 3 depicts an exemplary rewards program computer system according tovarious embodiments of the disclosure;

FIG. 4 depicts an exemplary system for performing a purchase transactionusing rewards points from multiple accounts and rewards programsaccording to various embodiments of the disclosure;

FIG. 5 depicts an exemplary system for performing a purchase transactionusing rewards points utilizing an aggregator computer system accordingto various embodiments of the disclosure;

FIG. 6 depicts an exemplary system for performing a purchase transactionusing rewards points utilizing card transaction authorization and/orsettlement processes according to various embodiments of the disclosure;

FIG. 7 depicts an exemplary user interface for requesting a purchaseaccording to various embodiments of the disclosure;

FIG. 8 depicts an exemplary user interface with the option to pay withrewards points or an account according to various embodiments of thedisclosure;

FIG. 9 depicts an exemplary user interface with the option to pay withrewards points or an account according to various embodiments of thedisclosure;

FIG. 10 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying cash values ofrewards points according to various embodiments of the disclosure;

FIG. 11 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying rewards pointsaccording to various embodiments of the disclosure;

FIG. 12 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying text rewardspoints allocations according to various embodiments of the disclosure;

FIG. 13 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying text rewardspoints allocations according to various embodiments of the disclosure;

FIG. 14 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying visual rewardspoints and account allocations according to various embodiments of thedisclosure;

FIG. 15 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying visual rewardspoints and account allocations according to various embodiments of thedisclosure;

FIG. 16 depicts an exemplary user interface with the option to pay withrewards points from multiple rewards programs displaying pie chartallocations according to various embodiments of the disclosure;

FIG. 17 depicts an exemplary flow chart which illustrates an exemplarymethod for performing a purchase transaction using rewards pointsaccording to various embodiments of the disclosure;

FIG. 18 depicts an exemplary flow chart which illustrates an exemplarymethod for performing a purchase transaction using rewards pointsaccording to various embodiments of the disclosure;

FIG. 19 depicts exemplary customer accounts data according to variousembodiments of the disclosure;

FIG. 20 depicts exemplary rewards program participation data accordingto various embodiments of the disclosure; and

FIG. 21 depicts exemplary rewards information data according to variousembodiments of the disclosure.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENT(S)

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specificembodiments and details involving systems and methods for performing apurchase transaction using rewards points. It should be appreciated,however, that the present disclosure is not limited to these specificembodiments and details, which are exemplary only. It is furtherunderstood that one possessing ordinary skill in the art, in light ofknown systems and methods, would appreciate the use of the invention forits intended purposes and benefits in any number of alternativeembodiments, depending on specific design and other needs.

Numerous financial institutions, such as credit card companies andbanks, as well as other entities like airline carriers, hotels, andretailers, offer membership rewards programs (also known as “loyaltyprograms”). These programs may reward participants with rewards“points,” such as numerical points or airline miles, for variousactivities, such as purchasing merchandise or services from merchantsusing a qualified account, such as a debit or credit account. Forexample, a participant in a rewards program may use a transaction cardassociated with the qualified account and be rewarded with acorresponding number of points for using the card. A merchant may alsoadminister its own rewards program whereby customers can accumulatepoints on items they buy from the merchant. Other programs may offerother types of rewards, incentives, or the like. For example, somerewards programs may return to a participant a predetermined percentageof a transaction amount or of an amount spent during a predeterminedperiod (referred to as “cash back”) either as a credit to an account orby check. Others may offer participants discounts or coupons on selectmerchandise or services and/or provide complimentary merchandise orservices. As used herein, the term rewards points may include any unitor currency of rewards accumulated in a rewards program, including, forexample and without limitation, points, bonus points, club points, andairline miles. Rewards points may also include cash in any formaccumulated in a rewards program.

Rewards points may accrue at a rate specified by the entity providingthe rewards program. For example, a participant may earn one point forevery dollar spent using a particular account or may receive onefrequent flyer mile for every mile traveled on a qualified flight. Someentities may restrict purchasing to particular merchants to earn rewardspoints, whereas other entities may have no such restrictions. Themaximum rewards points a participant can earn annually may be unlimitedor the provider may set specific limits. Additionally, rewards pointsmay not accumulate on cash advances, convenience checks, balancetransfers, fees, or adjustments, depending on the provider of therewards program, for example. When merchandise purchased with arespective account is returned, the account credit may also result in areduction of rewards points.

Various restrictions may also be placed on a rewards program such thatrewards points may only be “redeemed” for certain rewards at certaintimes and under certain conditions. Rewards program participants mayneed to accumulate a certain amount of rewards points over time to beable to redeem the points for merchandise or services. For example, aparticipant may need a certain number of rewards points to receive adesired reward or a certain number of frequent flyer miles to receive afree flight. Depending on the program, only certain merchants may beconsidered qualified merchants with whom rewards points may be redeemedtoward a purchase (e.g., a merchant offering a rewards program mayprohibit its points from being used to buy an item from a competitor).Other types of rewards points may be used for any purchase. Rewardspoints may also expire if they are not redeemed within a designatedperiod of time. A participant may be notified of any such conditions orrestrictions in advance. Also, any entity involved in the accrual orredemption of rewards points may place conditions or restrictions on theredemption of those points.

It will be understood by those of ordinary skill in the art that anamount of rewards points may have a corresponding cash equivalent valuefor which the rewards points may be redeemed. For example, 100 rewardspoints may be “worth” one dollar or 1000 airline miles may be “worth” 50dollars. The ratio of rewards points to cash (e.g., 100 rewards pointsfor one dollar) may be set by any entity associated with the rewardsprogram, such as the rewards program provider or the merchant with whichthe customer is attempting to redeem his or her points. The cashequivalent of rewards points may also differ depending on how theparticipant chooses to redeem the points. For example, the participantmay receive $50 by simply exchanging points for cash or may insteadreceive a $100 discount on the participant's next qualifying purchase.In that way, a merchant offering a rewards program may encourage itscustomers to buy more in the future and thereby increase its sales.

It will also be recognized that a customer may accumulate small amountsof rewards points in multiple rewards programs that he or she is notreadily able to redeem for various reasons. For example, a customer maydecide to register with one airline's rewards program for just oneflight and receive 100 frequent flyer miles, but the airline may require100,000 miles in order to receive any type of reward, such as a freeflight. A customer may also have rewards points that are about to expireor may be unaware of rewards points in the many different rewardsprograms in which he or she is participating. In these ways, thecustomer may miss valuable opportunities to redeem rewards points thathe or she accumulated over time. Providing a mechanism for rewardsredemption in such situations may benefit the customer by giving thecustomer value for rewards points that might otherwise have beenoverlooked. It may also encourage loyalty to the rewards programprovider and/or merchant with which the customer redeems his or herpoints.

Customers also may be unable to redeem rewards points in another similarscenario. Specifically, a customer may have accumulated a small amountof points in one rewards program and a small amount of points in anotherrewards program, which by themselves are not redeemable. However, bycombining the two sets of rewards points, the customer may have enoughto buy a product or service that he or she desires. Providing amechanism for rewards redemption in these circumstances, particularly atthe point of sale for the customer, may benefit the customer as well.

FIGS. 1 through 6 depict exemplary embodiments of systems for performinga purchase transaction using rewards points according to variousembodiments of the disclosure. The systems may involve variousnetwork-enabled computer systems to process instructions for performinga purchase transaction using rewards points, including, as depicted inFIG. 1, for example, a customer computer system 101, a merchant computersystem 102, and a rewards program computer system 103. As referred toherein, a network-enabled computer system may include, but is notlimited to: e.g., any computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer(PC), a workstation, a mobile device, a phone, a handheld PC, a personaldigital assistant (PDA), an automated teller machine (“ATM”), a thinclient, a fat client, an Internet browser, or other device. Thenetwork-enabled computer systems may execute one or more softwareapplications to, for example, receive data as input from an entityaccessing the network-enabled computer system, process received data,transmit data over a network, and receive data over a network. The oneor more network-enabled computer systems may also include one or moresoftware applications to enable the performance of a purchasetransaction using rewards points, as described herein.

The components depicted in FIGS. 1 through 6 may store information invarious electronic storage media, such as, for example, a rewardsprogram storage mechanism 107 and a merchant storage mechanism 105depicted in FIG. 1. It is well-known in the art that electronicinformation, files, and documents may be stored in various ways,including, for example, a flat file, indexed file, hierarchicaldatabase, relational database, such as a database created and maintainedwith software from, for example, Oracle® Corporation, Microsoft® Excelfile, Microsoft® Access file, or any other storage mechanism.

The components depicted in FIGS. 1 through 6 may be coupled via one ormore networks. As referred to herein, a network may include, but is notlimited to: e.g., a wide area network (WAN), a local area network (LAN),a global network such as the Internet, a telephone network such as apublic switch telephone network, a wireless communication network, acellular network, an intranet, or the like, or any combination thereof.In various exemplary embodiments, a network may include one, or anynumber of the exemplary types of networks mentioned above, operating asa stand alone network or in cooperation with each other. Use of the termnetwork herein is not intended to limit the network to a single network.The components depicted in FIGS. 1 through 6 may communicate byelectronic transmission through the one or more networks mentionedabove, by physical delivery, or by any other communication mechanism.Communication between two components depicted in FIGS. 1 through 6 mayalso include communication with any other entities between the twocomponents.

In various exemplary embodiments, customer computer system 101 may be acomputer system associated with or operated by a customer, e.g. anindividual or entity that desires to conduct a purchase transaction. Thecustomer may, for example, desire (at least initially) to conduct apurchase transaction using an account with an account provider. As usedherein, the term account may include any place, location, object,entity, or other mechanism for holding money or performing monetarytransactions in any form, including, without limitation, electronicform. An account may be, for example, a prepaid card account, storedvalue card account, debit card account, check card account, payroll cardaccount, gift card account, prepaid credit card account, charge cardaccount, checking account, rewards account, line of credit account,credit account, mobile device account, or mobile commerce account. Anaccount provider may be, for example, a bank, other type of financialinstitution, or any other entity that offers accounts to customers. Anaccount may or may not have an associated card, such as, for example, acredit card for a credit account.

The customer associated with customer computer system 101 may conductfinancial transactions with one or more merchants using his or heraccount. For example, the customer may desire to purchase goods orservices from a merchant. To do so, the customer may use a uniqueaccount identifier associated with the customer's account, which may beany sequence of letters, numbers, characters, or symbols of any lengthassociated with a payment mechanism, including, without limitation, acredit card, debit card, smart card, charge card, or any other mechanismfor making payment. The payment mechanism may be issued to the customerby the corresponding account provider. For example, the customer may beissued a credit card that allows the customer to make purchases oncredit up to a specified dollar limit and repay the account provider forthose purchases over time by making monthly payments. The accountprovider may pay for the purchases of the customer at the time ofpurchase on behalf of the customer and charge the customer interest forusing its credit services. Also, the customer may use a charge cardwherein the balance of the customer's card may be paid off monthly or adebit card wherein amounts for the customer's purchases may beelectronically debited from a checking or other account held by thecustomer with the account provider.

To make a purchase, the customer may, for example and withoutlimitation, swipe his or her credit card in person at the location of amerchant using a register, card payment terminal, ATM, or point of sale(POS) system, which may read the account identifier from the magneticstripe on the card. Also, the account identifier may be provided via abar code on the card. Also, the customer may provide a merchant with theaccount identifier over the telephone using a Voice Response Unit (VRU).Also, the account identifier may be provided via radio-frequencyidentification (RFID), near field communication (NFC), or otherautomatic identification mechanisms. Also, an account identifier may beassociated with biometric information provided by a customer (e.g.,fingerprint, iris scan, signature, voice). Various mechanisms foraccepting an account identifier as payment will be recognized by thoseskilled in the art, including, for example, transaction processingequipment and software provided by, for example, VeriFone, Inc. of SanJose, Calif.

The customer may also initiate a purchase transaction electronicallyusing customer computer system 101. Customer computer system 101, whichmay be, for example and without limitation, a personal computer orwireless/mobile device running a web browser program, may communicatewith merchant computer system 102 by electronic transmission overnetwork 104, such as the Internet. A web browser program on customercomputer system 101 may connect to a server of merchant computer system102 and request the Uniform Resource Locator (URL) of a web page fromthe server. The server may receive the request, process the request,retrieve or create the requested web page (e.g., a web page showing theitem to be purchased, a price, and a choice of payment mechanisms), andtransmit the requested web page to customer computer system 101. The webbrowser program may receive the web page and render it on a monitor orscreen. The customer may then interact with the web page by, forexample, clicking on buttons or activating links associated with the webpage or entering information with a keyboard. The web browser programmay interpret this interaction and send information back to the serverto perform various actions as instructed by the customer. For example,the customer may enter his or her account identifier and/or otherinformation associated with the desired purchase on the web page andclick a button to initiate the purchase. Examples of commercial webbrowser programs suitable for this purpose are Internet Exploreravailable from Microsoft® Corporation, Safari® available from Apple®,Inc., and Firefox® available from Mozilla Corporation. The web pagesdescribed above may be, for example, HTML (Hypertext Markup Language),XML (Extensible Markup Language), ASP (Active Server Page), Java,Javascript, XHTML (Extensible HyperText Markup Language), or Ajax(Asynchronous JavaScript and XML) files, or any other file format thatallows web pages or portions of web pages to be rendered in a webbrowser. It will be recognized by those skilled in the art that varioustools are readily available to create and render web pages.

Various other mechanisms for conducting financial transactions will berecognized by those skilled in the art. Items may be purchased bycharging an amount to a mobile device, such as a cellular phone, PDA, orsmart phone, using various known mechanisms for mobile commerce(otherwise known as “m-commerce”). For example, a customer may use asoftware application on a mobile device to charge from the mobiledevice's account or pre-loaded RFID chip. Also, various alternativepayment services may be utilized, such as, for example, PayPal, PayPalMobile, Obopay, and Google Checkout. These services may be accessed fromthe customer computer system and allow the customer to pay for atransaction or transfer money in various ways without using his or hersensitive financial information, such as credit card numbers.

It will also be understood that although a purchase transaction isdescribed herein, any type of financial transaction may be performed,such as, for example, a purchase, charge, cash advance, cash withdrawal,loan, payment, bill payment, check, debit, credit, deposit, or directdeposit. It will further be recognized that the systems for usingrewards points to conduct financial transactions, as described infurther detail below, may be provided in conjunction with any mechanismdescribed above.

The customer associated with customer computer system 101 may choose toparticipate in a rewards program provided by a rewards program provider,which may operate or be associated with rewards program computer system103. As described above, the customer may accumulate rewards points bymaking qualifying purchases, performing other financial transactions, orengaging in any other activity. It will be recognized that any entity orindividual may operate a rewards program and associated rewards programcomputer system 103. For example, an account provider may issue a creditcard with an associated rewards program. The participating customer maythen earn rewards points on purchases that he or she makes using thecard (e.g., 100 points for every dollar spent). The account provider mayalso be a bank and may reward its customers with rewards points forAutomated Clearing House (ACH) transactions that they conduct using thebank's routing number and their account numbers. Also, the rewardsprogram provider may be a retail or entertainment merchant that rewardsits customers for loyalty purchases. A customer in that situation mayearn points (e.g., 10% off coupon for every $100 spent) by, for example,swiping a club card every time he or she makes a purchase at one of themerchant's retail locations. Rewards points may also be accumulated forpurchases without any link to a card. Also, the rewards program may be afrequent flyer program operated by an airline carrier. A customer inthat situation may earn frequent flyer miles by using an identifier(e.g., account number, rewards code) every time he or she purchases aflight from the carrier. Also, the rewards program provider may be aconsumer packaged goods manufacturer. For example, a customer mayregister with the entity (e.g., a beverage manufacturer) and accumulaterewards points by entering on a web page codes that are printed on theretail products that he or she purchases (e.g., a numerical code printedon each bottle cap of a soft drink that the customer purchases). Therewards program provider may be any other entity as well.

It will be recognized that any type of account or other paymentmechanism may be associated with a rewards program. Such paymentmechanisms may include, for example and without limitation, transactioncards, transaction cards capable of communicating via RFID or NFC,alternative payment service providers like PayPal, Obopay, and GoogleCheckout, biometric payment service providers, and mechanisms usingalternative payment networks, such as wireless service providers.

In various exemplary embodiments, a mechanism may be provided whereby acustomer may use rewards points that he or she has accumulated over timeto purchase products and services. As described in reference to FIG. 1,customer computer system 101 may first request to make a purchase fromthe merchant associated with merchant computer system 102 by, forexample, the customer clicking on a web page of the merchant and thecustomer's web browser program providing the request to the merchant'sserver over network 104. Also, the customer may request to transfermoney or make a purchase using a mobile device. The purchase request mayinclude information regarding the customer and his or her desired methodof payment (e.g., an account identifier). For example, the customer mayenter his or her credit card number on a web page. Also, the customermay have already provided such information to merchant computer system102 prior to making the purchase request. For example, the customer mayhave previously registered his or her credit card number with merchantcomputer system 102 via a web page submission or telephone call. In thatscenario, the web page provided by merchant computer system 102 mayallow the customer to simply select the previously registered accountnumber rather than inputting a new payment mechanism. The storage ofcustomer account information will be described in reference to FIG. 2.

FIG. 2 depicts an exemplary merchant computer system 102 and merchantstorage mechanism 105 for performing a purchase transaction usingrewards points according to various embodiments of the disclosure.Merchant computer system 102 may include one or more of the followingmodules: a request module 108, a determination module 109, a transactionmodule 110, a selection module 111, a payment module 112, and a userinterface module 130. One or more of the modules may electronicallycommunicate with each other and/or other entities via a communicationmechanism 113, such as a data communication bus or one or more externalnetworks as defined herein, including network 104 and network 106. Themodules may each be a computer program or an appropriately programmedcomputer, such as a mainframe or personal computer, or may include aplurality of such computers cooperating to perform the functionalitydescribed herein. The modules may also communicate with merchant storagemechanism 105, which may include customer accounts data 114, rewardsprogram participation data 115, and rewards information data 116, asdescribed herein.

Merchant computer system 102 may store the customer's accountinformation as customer accounts data 114 either at the time of purchase(if provided with the purchase request) or prior to the purchase (if thecustomer registers beforehand). Customer accounts data 114 may store,for example, customer names, addresses, phone numbers, accountidentifiers, account numbers, account expiration dates, and any otherinformation associated with an account held by a customer. Customeraccounts data 114 may be stored in merchant storage mechanism 105 or maybe stored in any other storage mechanism associated with or remote tomerchant computer system 102. In various exemplary embodiments, anaccount identifier may comprise a bank identification number (BIN),which may be a six digit prefix of a credit card number or debit cardnumber. A BIN may be used to identify the account provider for theassociated account (or another entity, such as a card association), aswell as to determine the type of account. As described in greater detailbelow, a BIN (or any other identifier associated with the customerand/or an account held by the customer) may be used to determine if thecustomer has any associated rewards program(s).

FIG. 19 depicts exemplary customer accounts data. Customer accounts data900 may comprise entries 909-912 for particular stored customeraccounts, as described herein, wherein each is given an entry number901. For example, entry 909 may correspond to an account held by thecustomer “John Doe.” Each entry may comprise information associated witha particular account and customer, such as customer name 902, address903, phone number 904, account number 905, identifier 906, expirationdate 907, and account preferences 908. Identifier 906 may be the BIN foreach stored account. For example, entry 909 may correspond to an accountwith an account number of 1234123412341234 and BIN of 123412 (i.e., thefirst six digits). Account preferences 908 may store various accountpreferences set by the customer (e.g., to receive periodic updates fromthe merchant with information about new products, preferences for anaccount screen user interface).

Returning to FIG. 2, request module 108 may receive a purchase requestfor a purchase using a particular account. Determination module 109 maythen determine whether the account is associated with a rewards programwith accumulated rewards points. To do so, merchant computer system 102may access rewards program participation data 115. Rewards programparticipation data 115 may include various account numbers oridentifiers (e.g., BINs) and an indication as to what rewards programthey are associated with (if any). For example, the indication may be arewards program name or identifier. Rewards program participation data115 may be stored in merchant storage mechanism 105 or may be stored inany other storage mechanism associated with or remote to merchantcomputer system 102.

FIG. 20 depicts exemplary rewards program participation data. Rewardsprogram participation data 920 may comprise entries 909-912 forparticular stored identifiers (e.g., BINs) and associated lookupinformation, as described herein, wherein each is given an entry number921. For example, entry 927 may correspond to the identifier “123412,”which may be a BIN in various exemplary embodiments. Each entry maycomprise lookup information, such as identifier 922, rewards programname 923, rewards program provider 924, rewards program identifier 925,and rewards program type 926.

It will be recognized that any type of identifier may be used todetermine if the customer has any associated rewards program(s). Theidentifier may be associated with a payment type, such as a credit cardor debit card. In various exemplary embodiments, the identifier may be aBIN or full sixteen digit credit card number. The identifier may also beinformation associated with a customer but not a particular payment type(e.g., a customer name). For example, in the consumer packaged goodsmanufacturer example described above, a customer may participate in arewards program and accumulate rewards points by notifying themanufacturer of the products that he or she purchases (e.g., beverages).The customer may use some identifier, such as an e-mail address,username, or customer code, to enter product codes onto a web pageand/or redeem accumulated rewards points, for example. In that case, theidentifier, as well as any associated customer information, may beprovided to merchant computer system 102 by the rewards program provider(e.g., the beverage manufacturer), the customer, a trusted third party,or any other entity with access to such information. Merchant computersystem 102 may store the information as rewards program participationdata 115.

Again returning to FIG. 2, if merchant computer system 102 determinesthat the provided identifier (e.g., BIN) has no associated rewardsprogram (e.g., there is no corresponding entry in rewards programparticipation data 115), it may complete the customer's desired purchasetransaction as requested (e.g., through well-known authorization andsettlement procedures for credit cards). If, however, the providedidentifier (e.g., BIN) has one or more associated rewards programs(e.g., there is at least one corresponding entry in rewards programparticipating data 115), transaction module 111 may provide the optionto pay for the transaction with the provided account or with rewardspoints accumulated in the associated rewards program. To do so, merchantcomputer system 102 may retrieve information from rewards informationdata 116. Rewards information data 116 may store the name of thecustomer's rewards program, the name of the rewards program provider,the number of points accumulated, the cash value equivalent of thosepoints, a conversion ratio for converting between rewards points andcash, and any other information associated with the rewards program oraccumulated rewards points that may be helpful in providing the optiondescribed above. Rewards information data 116 may be stored in merchantstorage mechanism 105 or may be stored in any other storage mechanismassociated with or remote to merchant computer system 102.

FIG. 21 depicts exemplary rewards information data. Rewards informationdata 950 may comprise entries 960-963 for particular rewards pointsentries, as described herein, wherein each is given an entry number 951.For example, entry 960 may correspond to the rewards points thatcustomer John Doe accumulated in the “ABC Rewards” program. Each entrymay comprise rewards information, such as customer name 952, accountnumber 953, rewards program name 954, rewards program provider 955,points accumulated 956, cash value equivalent 957, conversion data 958(e.g., a 100:1 conversion ratio), and redemption restrictions 959. Asdepicted in FIG. 20, customer John Doe may have accumulated 12,500frequent flyer miles, which may correspond to $125.00 (100:1 conversionratio), and may not be able to redeem his points until he hasaccumulated more than 20,000 miles. In various exemplary embodiments,conversion data associated with a particular rewards program may be asimple ratio or percentage for converting between rewards points andcash. It may also be a more complicated formula set by the rewardsprogram provider or another entity. Also, conversion data may be anyinformation used to convert between one “currency” and another, whether“hard” currency (e.g., dollars, euros, pounds, yen) or currency used byany rewards program provider (e.g., points, miles, bottle cap codes).Also, conversion data, such as a ratio, may change over time and may besubject to various conditions and restrictions. For example, a rewardsprogram provider may run a promotion whereby customers may redeemrewards points at a more favorable ratio for a limited period of time.

It will be recognized that although exemplary customer accounts data,rewards program participation data, and rewards information data aredepicted in FIGS. 19 through 21, any type of data format or storagemechanism may be used.

Returning to FIG. 2, merchant computer system 102 may process andprovide rewards information to customer computer system 101 in variousways. Merchant computer system 102 may also calculate the number ofrewards points necessary to buy the requested item using conversiondata, as described above, and display that information as well. Forexample, merchant computer system 102 may calculate the amount ofrewards points that are the cash equivalent of a purchase amount basedon a ratio or formula in the conversion data and display thatinformation to the customer. Merchant computer system 102 may alsodetermine whether any restrictions or conditions should apply to the useof rewards points to make a purchase, as described above, and displaythat information or restrict a transaction accordingly. It will also beunderstood that while merchant computer system 102 is described hereinas determining whether the customer has an associated rewards programand retrieving rewards information for the customer's rewards points,similar actions may also be performed by the customer computer system101. For example, customer computer system 101 may be associated withits own storage mechanism for storing customer accounts data, rewardsprogram participation data, and/or rewards information data. In thatway, a customer may accumulate points on his or her own computer systemand communicate data to and from other systems, such as merchantcomputer system 102 and rewards program computer system 103, asnecessary.

Providing the option to pay with rewards points will be furtherdescribed in reference to FIGS. 7 through 9. FIG. 7 depicts an exemplaryuser interface 200 for requesting a purchase, which may be provided tocustomer computer system 101 by user interface module 130 of merchantcomputer system 102. User interface 200 may be, for example, aninteractive web page displayed on a screen of customer computer system101 from web page data provided by merchant computer system 102. Userinterface 200 may include an item description 201 for the item that thecustomer desires to purchase, a price 202 for the item, and inputs forthe customer's first name 203, last name 204, street address 205, city206, state 207, and zip code 208. User interface 200 may also includepayment inputs associated with a transaction card (e.g., credit or debitcard) that the customer may use as payment, including inputs for cardtype 209, card number 210, expiration date 211, and card identificationnumber 212. The customer may input information into user interface 200with a keyboard or mouse and click purchase button 213 to purchase thedesired item with a card. The inputted information may then be providedby customer computer system 101 to merchant computer system 102electronically. Merchant computer system 102 may then process theinformation by determining whether the provided account has anassociated rewards program with rewards points, as described herein, andprovide the option to pay for the transaction with the account or withrewards points.

FIG. 8 depicts exemplary user interface 200 with the option to pay withrewards points or an account, after the customer has inputted andsubmitted the required information (e.g., card number, expiration date).Merchant computer system 102 may then return data to customer computersystem 101 to modify user interface 200 to allow the customer to chooseto pay for the transaction with rewards points instead. As depicted inFIG. 8, an option description 214 reads: “Would you like to pay for thispurchase with 47,500 frequent flyer miles from your ABC Airline RewardsAccount instead?” Merchant computer system 102 may have thereforedetermined, as described herein, that the account listed in card numberinput 210 has an associated frequent flyer miles program with ABCAirline with accumulated rewards points and that $47.50 corresponds to47,500 in frequent flyer miles. A rewards points selector button 215 maybe clicked on the customer's computer screen to pay for the purchasewith rewards points. Also, the customer may click on purchase button 216to purchase the item with the inputted account instead.

It will be recognized that user interface 200 may be one or moreinteractive web pages downloaded and displayed on a personal computer ormobile device, for example, or any other mechanism for displaying andreceiving information for performing a purchase transaction usingrewards points. For example, user interface 200 may comprise a popupwindow, Windows ActiveX control, or Java applet displayed on thecustomer's computer screen, which allows the customer to select to paywith rewards points or an account. Also, user interface 200 may bedirectly integrated with an existing e-commerce platform such that anycustomer that uses the platform may pay with rewards points or anaccount using the platform. Also, a rewards program provider may provideto the merchant an application programming interface (API) withfunctionality for determining whether an account has an associatedrewards program and presenting such information to the customer. Also,user interface 200 may be displayed on an ATM.

Also, user interface 200 may be integrated and deployed with variousalternative payment service providers, such as PayPal, Obopay, andGoogle Checkout. In that case, merchant computer system 102 maycommunicate with an alternative payment service provider computersystem, which may itself provide user interface 200 to customer computer101. Also, the alternative payment service provider computer system maycommunicate information to merchant computer system 102 so that merchantcomputer system 102 can allow customers to pay for purchases withrewards points via the alternative payment service provider. Forexample, merchant computer system 102 may communicate with thealternative payment service provider computer system prior to acustomer's purchase to establish the functionality for allowing acustomer to pay for a purchase with rewards points or may communicatewith the alternative payment service provider computer system in realtime at the time of purchase. It will be understood that it may bebeneficial for an alternative payment service provider to allow acustomer to pay with multiple forms of currency, such as cash in variousforms (e.g., dollars, euros, pounds, yen), credit, or rewards points.Allowing customers to pay with rewards points may be less expensive forthe alternative payment service provider than allowing customers to paywith cash. Also, an alternative payment service provider may gather agreat deal of information about its customers' buying habits by allowingmany different payment mechanisms, which it may then use to targetpromotional efforts or sell to merchants.

FIG. 9 depicts an exemplary user interface 200 with the option to paywith rewards points or an account using information previously providedby the customer. For example, the customer may have provided themerchant with account information (e.g., a credit card number andexpiration date) and the merchant may have also received rewards programparticipation data and rewards information. In that way, the merchantmay know in advance that a customer has rewards points and an accountavailable to make a purchase and may therefore offer both options. Asdepicted in FIG. 9, the customer may have, for example, navigated to aweb page for a specific book that he or she may desire to purchase. Userinterface 300 may then display an item description 301, a price 302, anumber 303 identifying the specific item, an item image 304, a rewardsexplanation 305. User interface 300 may also include a rewards pointspayment input 306 and an account payment input 307. As depicted in FIG.9, rewards explanation 305 may display: “You currently have 50,000frequent flyer miles available in your ABC Airline Rewards Account.” Thecustomer may then choose to buy the item with 47,500 miles by selectingrewards point payment input 306 or may choose to buy the item with hisor her credit card by selecting account payment input 307. Informationregarding both choices may be provided by the customer or any otherindividual or entity with access to such information prior to userinterface 300 being displayed, as described herein.

In various exemplary embodiments, rewards program participationinformation (e.g., the information stored in rewards programparticipation data 115) and/or rewards information (e.g., theinformation stored in rewards information data 116) may be provided tothe merchant by various computer systems, including rewards programcomputer system 103 and/or customer computer system 101, as well asother entities, in various ways at various times. The time when rewardsprogram participation information and/or rewards information is providedmay depend on the processing speed and/or capacity of rewards programcomputer system 103 and merchant computer system 102, among otherentities. For example, rewards program computer system 103 may provide adaily batch file of BINs and associated rewards information, whichmerchant computer system 102 may use to populate rewards programparticipation data 115 and rewards information data 116. The informationmay also be provided on a real-time “as needed” basis. In variousexemplary embodiments, rewards program participation information may bereceived by merchant computer system 103 in daily batch files andrewards information may be received on an “as needed” basis. Providingrewards program participation information and rewards information willbe further described in reference to FIG. 3.

FIG. 3 depicts an exemplary rewards program computer system 103according to various embodiments of the disclosure. Rewards programcomputer system 103 may include one or more of the following modules: arequest module 117, an information module 118, a selection module 119,and a payment module 120. One or more of the modules may electronicallycommunicate with each other and/or other entities via a communicationmechanism 121, such as a data communication bus or one or more externalnetworks as defined herein, including network 106. The modules may eachbe a computer program or an appropriately programmed computer, such as amainframe or personal computer, or may include a plurality of suchcomputers cooperating to perform the functionality described herein. Themodules may also communicate with rewards program storage mechanism 107,which may include rewards information data 121 and rewards programparticipation data 122, as described herein.

Upon receiving a purchase request from customer computer system 101,merchant computer system 102 may determine the appropriate rewardsprogram provider based on the customer's account identifier (e.g., BIN,customer code, e-mail address) and request rewards program participationinformation and/or rewards information from rewards program computersystem 103. Request module 117 may determine account information for theaccount provided by the customer by, for example, receiving the BIN forthe customer's credit card. Rewards program computer system 103 may thendetermine whether the provided BIN has an associated rewards program bysearching rewards program participation data 122, which may comprise aset of BINs and associated rewards program names or identifiers (e.g.,the data described in reference to FIG. 20). As described above, whetherthe customer has an associated rewards program may be determined bysearching rewards program participation data 122 for an identifierassociated with a payment type or an identifier associated with thecustomer. For example, rewards program participation data 122 may bestored by a trusted third party that collects customer information.Rewards program computer system 103 in that case may request thenecessary information from that computer system.

If a match is found, rewards program computer system 103 may retrieverewards information (e.g., the name of the customer's rewards program,the name of the rewards program provider, the number of pointsaccumulated, the cash value equivalent of those points, a conversionratio for converting between rewards points and cash, and any otherinformation associated with the rewards program) from rewardsinformation data 121 (e.g., the data described in reference to FIG. 21).Information module 118 may provide rewards program participationinformation and/or rewards information to merchant computer system 102.It will be recognized that rewards information may therefore be providedto the merchant on a real-time or near real-time basis “as needed” uponthe merchant receiving a purchase request. Rewards information data 121and rewards program participation data 107 may be stored in rewardsprogram storage mechanism 107 or may be stored in any other storagemechanism associated with or remote to rewards program computer system103.

In various exemplary embodiments, the rewards program associated withrewards program computer system 103 may be operated by or associatedwith the account provider that issued the account initially provided bythe customer. It will be recognized, however, that the rewards programmay be operated by any other type of entity, including a merchant orindependent entity, as well.

Returning to FIG. 2, after the option is provided to the customer to payfor the purchase with an account or rewards points, selection module 119of merchant computer system 102 may receive a selection from customercomputer system 101. For example, the customer's web browser may displaytwo options and the customer may select one or the other by clicking ona corresponding link or button, as depicted in FIG. 8. If merchantcomputer system 102 determines that the customer decided not to pay forthe purchase with rewards points, it may submit the charge forauthorization and settlement, provide the desired item to the customer,and receive payment from the account provider. If merchant computersystem 102 determines, however, that the customer decided to pay for thepurchase with rewards points, it may provide information notifyingrewards program computer system 103 that such a selection was made. Forexample, merchant computer system 102 may notify rewards programcomputer system 103 of the number of rewards points used or the cashequivalent value of the rewards points used for the purchase. Theprovided information may allow rewards program computer system 103 topay for the customer's purchase with rewards points, as describedherein. For example, if the customer initially attempted to complete thedesired transaction with a credit card but then selected the optioninstead to pay with rewards points, the customer's credit card may neverbe charged. Also, merchant computer system 102 may provide otherinformation to rewards program computer system 103, such as anypromotions, coupons, discounts, bonuses, or other incentives that wereselected by the customer for redeeming his or her rewards points.

Rewards program computer system 103 may then in turn reconcile thetransaction by, for example, reducing the number of rewards pointsavailable to the customer (e.g., deducting 47,500 frequent flyer miles)and paying the merchant the corresponding cash value of the redeemedpoints (e.g., $47.50). Various reconciliation mechanisms for paying cashto a merchant will be understood by those of ordinary skill in the art.For example, payment module 120 may cause an ACH credit to be made tothe merchant. Payment module 112 of merchant computer system 102 mayreceive such payment electronically. Also, where an alternative paymentservice provider, merchant processor, or wireless service provider isused for a purchase, as described herein, rewards program computersystem 103 may cause payment to be made to that entity (via anassociated computer system, for example), which may then in turn pay themerchant. In that case, the merchant may not know that a customer paidfor a transaction using rewards points. Various intermediary accountsmay also be used so that the merchant receives payment for a customer'suse of rewards points to make a purchase. It will be understood that themerchant associated with merchant computer system 102 (or any otherentity that providing goods or services to the customer) may be paid inany way for the rewards points that a customer uses to make a purchase.

Also, if merchant computer system 102 determines that the customerdecided to pay for his or her purchase with rewards points, merchantcomputer system 102 may still submit the charge for authorization andsettlement with the account that the customer initially provided butcredit the customer for the amount of the charge in various ways. Forexample, if a credit card number was initially provided for thepurchase, the full value of the purchase may be charged to thecustomer's credit card. Merchant computer system 102, however, may alsoprovide information notifying rewards program computer system 103 (orany other entity) that the customer's account should be credited forthat value. Such processing may be beneficial to take advantage ofpreexisting card transaction processing mechanisms (such as, forexample, those described herein in reference to FIG. 6), as well asfraud protection and merchant dispute handling provided by entitiesinvolved in card transaction processing.

In various exemplary embodiments, the components described in referenceto FIGS. 1 through 6 may perform various procedures to ensure thatrewards points are not incorrectly redeemed. For example, two merchantcomputer systems may receive a daily batch file of BINs and associatedrewards information, which informs the merchants that a particularcustomer has 25,000 rewards points available. The customer may thenpurchase an item from the first merchant using 25,000 rewards points,but the second merchant may not be aware of the transaction until thenext day. If the customer attempted to redeem the same 25,000 points fora purchase from the second merchant, the second merchant may incorrectlyallow the transaction to proceed. Such invalid redemption may beavoided, however, by the merchant computer system making “as needed”requests to the rewards program computer system to verify in real timethat the rewards points still remain. Also, transactions may not befully authorized until the next batch file is sent (e.g., a merchant maynot actually provide the purchased product until a transaction fullyclears). Also, the rewards program provider and merchant may negotiateoffline as to the best way to handle invalid rewards points redemptions.

In various exemplary embodiments, the components described in referenceto FIGS. 1 through 6 may also perform various procedures to determinewhether and how a particular customer should be provided the option topay for a purchase with rewards points. For example, merchant computersystem 102 may only provide the option in limited circumstances wherethe customer has enough rewards points to pay for the entire purchase orwhen the customer is a “preferred” customer because he or she has made acertain number of qualifying purchases in the past. Merchant computersystem 102 may even completely prevent customers from using rewardspoints to pay for purchases in certain circumstances or at certaintimes. Also, merchant computer system 102 may allow a registeredcustomer to “opt out” and not be provided the option to pay with rewardspoints for his or her purchases. Also, a customer may select varioususer preferences for the option with merchant computer system 102. Forexample, a customer may choose to be provided the option only when thepurchase is above or below a certain dollar amount.

Also, rewards program computer system 103 (or any other system) maydesignate certain merchants for offering enhanced value (e.g., rewardspoints are worth 25% more than usual if redeemed with the particularmerchant) or special incentives (e.g., rewards points are worth doubleduring a set of dates near the Christmas holiday) for customers' rewardspoints. Such information may be communicated to, for example, merchantcomputer system 102, as described herein. Also, rewards program computersystem 103 or merchant computer system 102 may not provide the option topay with rewards points in the user interface at various times and incertain circumstances (e.g., based on the value of the rewards points atthe particular time), but may allow the customer to choose to pay withrewards points by affirmatively selecting a particular option.

It will be understood by those of ordinary skill in the art that anytype of promotion, coupon, discount, bonus, other incentive, condition,or restriction may be placed on the option to pay with rewards points byany system, including those depicted in FIGS. 1 through 6, such asrewards program computer system 103 and merchant computer system 102.They may be, for example, time-specific, customer-specific, and/orproduct-specific. They may also be merchant trade promotions designed totarget particular customers based on the customers' buying behavior. Forexample, if a customer has bought a considerable amount recently from aparticular retailer, a rewards program provider may offer anadvantageous redemption (e.g., rewards points worth 25% more) if thecustomer buys in the future from a competitor with which the rewardsprogram provider has a relationship.

As described in further detail in reference to FIG. 4 and FIGS. 10through 16, a portion of both an account and rewards points may beselected, or rewards points from multiple rewards program providers maybe selected, by “splitting” the total amount of the purchase betweenthem and processing each separately. Merchant computer system 102 may inthat case provide to the customer the option to pay for a purchase withan account or rewards points, as described herein, and/or with rewardspoints from multiple rewards program providers and multiple accounts. Inreference to FIG. 4, the customer may have selected to pay for apurchase that has a total purchase amount (e.g., $47.50) with an amountfrom his or her account ($10.00), rewards points from a rewards programto which he or she belongs (e.g., 100 points), and rewards points fromanother additional rewards program to which he or she belongs (e.g.,17,500 frequent flyer miles). Such partial payment may be particularlybeneficial to a customer who has many different rewards programs and/ormany different accounts.

The account provider for the customer's account may operate or beassociated with an account provider computer system 123 and storagemechanism 125 for storing account information (e.g., amount currently inthe customer's checking account, credit limit for a credit card). One ormore additional rewards program providers may provide the additionalrewards program(s) and operate or be associated with additional rewardsprogram computer system(s) 124 a-n and corresponding storage mechanism126 a-n for storing rewards program participation information andrewards information. The operation of additional rewards programcomputer system(s) 124 a-n and storage mechanism 126 a-n may be similarto that of rewards program computer system 103 and rewards programstorage mechanism 107, as described herein. It will also be recognizedthat more than one account provider computer system may be used as well.

As described herein, merchant computer system 102 may receive a purchaserequest, determine an account identifier for the customer (by receivingit from the customer or retrieving it from a storage mechanism where thecustomer has registered an account, for example), provide the option topay with various accounts and/or rewards points, and receive acorresponding selection of multiple sources from the customer. Merchantcomputer system 102 may then communicate with the sources via network106 to complete the purchase transaction. For example, merchant computersystem 102 may submit authorization and settlement requests to accountprovider computer system 123 for $10.00 and may receive payment from theaccount provider for that amount. Merchant computer system 102 may alsoretrieve rewards program participation information and rewardsinformation for the rewards programs associated with rewards programcomputer system 103 and any of additional rewards program computersystem(s) 124 a-n, as described herein, and may notify each of thedesired allocation (e.g., 100 points to rewards program computer system103 and 17,500 frequent flyer miles to additional rewards programcomputer system 124 a). The applicable rewards programs may then reducethe customer's accumulated rewards points accordingly and cause paymentto be made to the merchant for the cash value corresponding to therewards points. It will be recognized that although a merchant isdescribed herein in reference to merchant computer system 102, anyentity involved in transaction processing may perform the abovefunctionality.

FIG. 10 depicts an exemplary user interface 400 with the option to paywith rewards points from multiple rewards programs displaying cashvalues of rewards points according to various embodiments of thedisclosure. User interface 400 may comprise a web page or other displayand input mechanism, such as, for example, a terminal at a merchantretail location or a screen on a wireless/mobile device. User interface400 may be displayed after a customer has selected a particular productor service to purchase and may comprise a price display 401 for thetotal purchase price of the transaction (e.g., $124.37). User interface400 may also comprise a set of linked program names 404, linked programnumbers 405, cash values 406, rewards program payment inputs 407, anaccount identifier 408, an account input 409, and a total allocatedamount 410. Linked program names 404 may comprise the names or titles ofvarious rewards programs to which the customer belongs, such as “FirstBank,” “First Hotel Chain,” “Second Airlines,” and the like. Rewardsprograms and accounts may be “linked” in the sense that the entityproviding user interface has information available regarding thecustomer's rewards program and accounts (e.g., by retrieving it from astorage mechanism, requesting it from a rewards program provider oraccount provider, or receiving it from the customer previously or at thetime of purchase). Linked program numbers 405 may comprise identifiersfor the various programs for the customer's convenience. As depicted inFIG. 10, portions of the linked program numbers may be crossed out sothat someone else viewing the customer's computer screen does not stealthem. Cash values 406 may list the cash value equivalents of the rewardspoints accumulated in each program. For example, the rewards pointsaccumulated in the “First Airlines” program may be redeemed for $237.00.As described herein, the information regarding the customer's variousrewards programs that is displayed on user interface 400 may beretrieved internally based on an account identifier provided by thecustomer (e.g., a BIN) or may be retrieved externally from theindividual rewards program providers or the customer. Account identifier408 may also identify an account that the customer may use to pay all ora portion of the transaction.

Rewards program payment inputs 407 and account input 409 may be textinput boxes for the customer to type in dollar amounts to allocate toeach rewards program and/or account to pay for the purchase. As depictedin FIG. 10, the customer may have selected to pay for the $124.37transaction with $21 worth of rewards points from the first “First Bank”program, $100.37 worth of rewards points from the second “First Bank”program, and $3 worth of frequent flyer miles from the “Second Airlines”program. The total amount currently allocated at the time may bedisplayed in total allocated amount 410 so that the customer knows howmuch he or she has allocated so far and how much remains to beallocated. As depicted in FIG. 10, the customer has allocated the full$124.37 amount and may then complete the transaction. Once input isreceived from the customer, information regarding the customer'sselections (e.g., how much was allocated to each rewards program and/oraccount) may be provided to computer systems associated with the rewardsprograms and accounts. In various exemplary embodiments, onlyinformation necessary to a particular reward program or account may beprovided (e.g., “Second Airlines” program would not know that thecustomer also spent $21 worth of rewards points from the first “FirstBank” program). As depicted in FIG. 10, information would be provided tocomputer systems associated with the “First Bank” and “Second Airlines”programs.

FIG. 11 depicts an exemplary user interface 500 with the option to paywith rewards points from multiple rewards programs displaying rewardspoints according to various embodiments of the disclosure. Userinterface 500 may comprise a customer display 501, a set of linkedprogram names 502, a set of linked program numbers 503, points availabledisplays 504, and rewards program payment inputs 505. Customer display501 may display the customer's name or information regarding his or heraccounts or any other information that might be useful to the customerin determining how to make the desired purchase. In contrast to userinterface 400 depicted in FIG. 10, user interface 500 may displayrewards points (available and allocated) rather than dollar amounts.Doing so may give additional information to the customer and allow himor her to make a better informed decision. For example, as depicted inFIG. 11, the customer may realize that he or she has a small number ofrewards points (100 points) available in the first “First Bank” programand may therefore desire to use up all 100 points in the currentpurchase. User interface 500 may also comprise a total points neededdisplay 506, a total points allocated display 507, and a points neededdisplay 509, which may each dynamically change in response to textentries from the customer into rewards program payment inputs 505. Totalpoints needed display 506 may also correspond to the purchase amount ofthe transaction. As depicted in FIG. 11, the customer has allocated 500points so far and may need to allocate 219 more points in order tocomplete the transaction. As a result, a purchase completion button 508may be inactive until the total points allocated matches the totalpoints needed.

In various exemplary embodiments, a user interface may display anindication regarding particular rewards points that the customer maywant to use immediately for various reasons. For example, if aparticular set of rewards points are a few days away from expiring, theuser interface displayed to the customer may display a popup windowalerting the customer to that fact. Also, if a certain set of rewardspoints are subject to an annual cap, the user interface may display anindication alerting the customer to that fact as well. Also, if arewards program provider is currently running a promotion or offering anextra coupon, discount, or other incentive for redeeming rewards points,the user interface may display an indication to alert the customer.

A user interface may also display information for intelligentlysuggesting to the customer particular redemption strategies, which maybe received from a merchant computer system or rewards program computersystem or created through processing at the customer computer systemwhere the user interface is displayed. Such redemption strategies may bedesigned to ensure the maximum benefit for the customer in using his orher rewards points to make purchases. For example, the earn rate for acustomer (e.g., the rate at which he or she accumulates points in arewards program) may change over time based on usage, status (e.g.,“silver” or “platinum” rewards programs), or other factors that make itparticularly advantageous to redeem or not to redeem certain points. Ifa customer tends to earn rewards points relatively quickly, it may bebeneficial to use those points right away so that the customer does notwaste points by reaching a cap imposed by the provider. Conversely, itmay be advantageous to keep accumulating rewards points rather thanusing them so that the customer can make a large purchase (e.g., ifthere is a minimum number of rewards points that can be redeemed at anyparticular time). Any computer system described herein may be programmedto take such factors into account and display in the user interfacevarious strategies or suggestions for the best ways to redeem thecustomer's rewards points. The indication may be in any format, such as,for example, flashing text, color coding, popup alerts, or lists ofrewards points ordered from best to worst. The information for providingsuch redemption strategies may also be received from various entities(e.g., a rewards program provider that may have information regardingthe customer's points accumulation tendencies, an account provider thatmay have information regarding the customer's financial history).

A user interface may also be used for customer contact and promotionalpurposes. For example, rewards information provided by a rewards programcomputer system to a merchant computer system for display on a userinterface, as described herein, may include promotions, such as specialoffers, ads, coupons, discounts, or other information. The promotionsmay be designed to encourage a customer to redeem certain rewards pointsfor various reasons, such as distressed inventory, for example. Also,the user interface may include ads for the rewards programs from whichthe customer may redeem his or her rewards points. Also, the userinterface may include links to the web pages of the various rewardsprograms or links to locations where the customer may update his or heruser profile with the rewards programs. Promotions provided in the userinterface may be based on the product or service desired by thecustomer, the rewards points and accounts available to the customer topay for the transaction, or any other information associated with thecustomer. In addition to a rewards program provider, a merchant may alsowant to include such promotional information in the user interface. Forexample, a merchant may receive a benefit from a rewards programprovider whenever points from the rewards program are redeemed. It maytherefore have an incentive to encourage customers to pay fortransactions using those points. Also, the user interface may includeinformation regarding a rewards program that may not even be displayedas an option for the customer. For example, the provider of the userinterface may make a “smart match” to a known rewards program that thecustomer may have overlooked by matching customer name or addressinformation stored locally or externally, as described herein. Theprovider may thereby help customers maximize their redemption of rewardspoints by locating rewards programs that they might have forgotten theyhad.

In various exemplary embodiments, allocations between rewards programsand accounts being used to pay for a purchase may interactively changeon a user interface in response to customer input into the userinterface. Modifying one allocation in response to a change in anothermay give the customer a better sense of how he or she should use rewardspoints and accounts to pay for a purchase and may be of great benefit tothe customer in making a financial decision. This feature will bedescribed in reference to FIGS. 12 through 15.

FIG. 12 depicts an exemplary user interface 600 with the option to paywith rewards points from multiple rewards programs displaying textrewards points allocations according to various embodiments of thedisclosure. User interface 600 may comprise a customer display 601, atotal points needed display 602, a set of linked program names 603, aset of linked program numbers 604, points available displays 605,rewards program payment inputs 606, a total points allocated display607, and a purchase completion button 608. The total points allocated intotal points allocated display 607 may remain static at the total pointsneeded (e.g., 12,725 points) in response to input from the user oranother entity. In that case, the customer may only change the pointamounts in rewards program payment inputs 606. For example, in referenceto FIG. 12, the customer may have initially chosen to use 1,000 pointsfrom the “First Bank” program and 11,725 points from the “Second Bank”program for a total of 12,725 points.

FIG. 13 depicts user interface 600 after the customer modified one ofthe point amounts in rewards program payment inputs 606. As depicted inFIG. 13, the customer have increased the allocation from the “FirstBank” program from 1,000 points to 5,000 points. User interface 600 maythen have automatically changed the points allocated to the “SecondBank” program from 11,725 points to 6,725 points. To do so, the computersystem providing user interface 600 may have performed a calculation todetermine that because the first allocation increased by 4,000 points,the second allocation should correspondingly be decreased by 4,000points so that the total remains the same. More complicated calculationsand rewards points-to-cash conversions may also be performed as well.Dynamically changing allocations in response to input from the customermay give the customer a better sense of how he or she should use rewardspoints and accounts to pay for a purchase and may be of great benefit tothe customer in making a financial decision. Also, the entity providinguser interface 600 may provide an initial “preferred” allocation basedon preferences set by the customer or based on a formula to determine anoptimal allocation (e.g., using rewards points from the program with theleast number of points first, using rewards points that have the bestconversion ratio for the current transaction or merchant). Also, theamounts displayed in user interface 600 may be dollar amounts or anyother amounts rather than rewards points, as described in reference toFIG. 10, for example.

FIG. 14 depicts an exemplary user interface 700 with the option to paywith rewards points from multiple rewards programs displaying visualrewards points and account allocations according to various embodimentsof the disclosure. User interface 700 may display a more complex seriesof rewards programs and accounts to be used in paying for a purchase.For example, the customer may have a large number of rewards programsand accounts and may benefit from an easy to use interactive userinterface for allocating between them. Rather than inputting text ofdollar amounts or point amounts, it may be advantageous for the customerto operate an interactive visual display whereby the results of changingone allocation can be easily viewed in the other allocations. Userinterface 700 may comprise a customer display 701, a set of linkedprogram names 702, a set of linked program numbers 703, a minimum valuedisplays 710, selection mechanisms 704, maximum value displays 711,allocation displays 712, a total purchase price display 709, and apurchase completion button 713. Each minimum value display 710 maycorrespond to the least amount of rewards points or cash value that maybe used to help pay for the desired purchase (e.g., zero points for“First Bank” program, $0.00 for the customer's credit card). Eachmaximum value display 711 may correspond to the greatest amount ofrewards points or cash value that may be used to help pay for thedesired purchase (e.g., 12,000 points for “First Bank” program, $247.52for the customer's credit card). In various exemplary embodiments, theminimum value for a particular rewards program may be the least amountthat is redeemable in the current transaction, while the maximum valuefor a particular rewards program may be the total amount of rewardspoints that that the customer has accumulated. The minimum and maximumvalues may also be subject to restrictions and conditions, as describedherein, which may be displayed on user interface 700 in the form of apopup window or other display (e.g., notifying the customer that aparticular set of rewards points will expire on a certain date). Also,the maximum value for a particular account may be the dollar amountcurrently available or the customer's credit limit.

Each selection mechanism 704 may comprise a mechanism for the customerto select on user interface 700 an amount of rewards points or cashvalue within a defined range. Each selection mechanism 704 may comprisea range indicator, such as range indicator 706, and a value selector,such as value selector 705. Range indicator 706 may correspond to theminimum and maximum values for the particular rewards program and may beappropriately sized and shaped to give the customer an accuraterepresentation (e.g., a range of 1000 points may appear larger than arange of 100 points). Value selector 705 may be positioned to correspondto the currently selected amount of rewards points or cash value for theparticular program and may be moved within the range of range indicator706 to select a different value. For example, the customer may drag anddrop value selector 705 with a computer mouse or finger on a touchscreen or the customer may also use left and right arrow keys on akeyboard. As depicted in FIG. 13, for instance, the customer may havemoved value selector 705 for the “First Bank” program all the way to theminimum position corresponding to zero points to be allocated and mayhave moved value selector 705 for the “First Airlines” program all theway to the maximum position corresponding to 17 frequent flyer miles.The currently selected amount of rewards points or cash value for aparticular program or account may be displayed in allocation display712. Also, other types of selection mechanisms may be used as well.

FIG. 15 depicts user interface 700 after one of the allocations waschanged. For example, the customer may have decided for various reasonsnot to use his or her frequent flyer miles in the “First Airlines”program and therefore reduced the allocation to that program to zeromiles. Upon receiving data indicating the change from the customer'scomputer system, the entity providing user interface 700 may have causedtwo other allocations to be changed so that the total value remains thesame, i.e., at the purchase price. Specifically, the allocation from the“Second Bank” program may have changed from 100 points to 500 points andthe allocation from the customer's credit card may have increased from$0.00 to $18.00. The particular changes made may be determined based oncustomer preferences, optimal allocations, or any other formula orprocedure for making allocations dynamically.

FIG. 16 depicts an exemplary user interface 800 with the option to paywith rewards points from multiple rewards points displaying pie chartallocations according to various embodiments of the disclosure. Userinterface 800 may comprise a customer display 801, total purchase pricedisplay 802, and allocation display 803. Allocation display 803 maycomprise a visual display, such as a pie chart, of the variouspercentage of rewards program and account allocations (e.g., how mucheach contributes to 100% of the purchase price). As depicted in FIG. 16,500 points from the “Second Bank” program contribute 62.5% of thepurchase price, 190 points from the “First Hotel Chain” programcontribute 25% of the purchase price, and $18.00 from the customer'scredit card contributes 12.5% of the purchase price. The allocationsdisplayed on user interface 800 may be moved and changed interactivelyby the customer (e.g., by dragging and dropping portions of a pie chartwith a computer mouse or touchpad) and may dynamically change inresponse to customer input, as described herein.

In various exemplary embodiments, a particular computer system maycollect and provide rewards information for a plurality of rewardsprograms. In reference to FIG. 5, merchant computer system 102 may havereceived a purchase request and may provide information associated withthe request to an aggregator computer system 127 via network 106. Theinformation may comprise, for example, one or more BINs or rewardsprogram identifiers provided by the customer. Based on the informationreceived from merchant computer system 102, aggregator computer system127 may communicate with various rewards programs and/or accountproviders to retrieve rewards information for providing the customerwith the option to pay for the purchase with various rewards points andaccounts. For example, a BIN corresponding to a customer credit card maybe received. The corresponding customer may have registered a number ofrewards programs and other accounts with aggregator computer system 127and provided instructions to make such programs and accounts availablein the future. Such instructions may be provided via a web page operatedby a server of aggregator computer system 127. Aggregator computersystem 127 may also store information received from a customer or anyother entity in a storage mechanism 130. Also, aggregator computersystem 127 may determine based on a particular BIN provided by merchantcomputer system 102 what rewards program computer system should becontacted regarding the purchase request. As depicted in FIG. 5,aggregator computer system 127 may communicate with rewards programcomputer system 103 when a certain BIN is received, but may communicatewith one or more additional rewards program computer system(s) 124 a-nwhen different BINs is received. Also, a plurality of BINs or otheridentifiers may be provided by merchant computer system 102 andaggregator computer system 127 may contact each associated rewardsprogram provider or account provider on behalf of the merchant. Also,aggregator computer system 127 may be independent or may itself beassociated with a rewards program in which the customer may accumulaterewards points. Also, utilizing the aggregator computer system 127described in reference to FIG. 5 may be advantageous because theaggregator entity may negotiate favorable conversion rates for itscustomers with a plurality of rewards program providers.

Also, aggregator computer system 127 may receive a customer selection ofamounts and/or rewards points from merchant computer system 102, asdescribed herein. Aggregator computer system 127 may then communicatewith the rewards programs and account providers that were selected tohelp pay for the purchase amount. For example, aggregator computersystem 127 may submit authorization and settlement requests for a creditcard portion to an account provider and may provide information torewards programs to reduce the customer's rewards points accordingly andcause payment to be made to the corresponding merchant for the points.

It will be understood by those of ordinary skill in the art that it maybe beneficial to a rewards program provider to participate in such asystem for performing a purchase transaction using rewards points, asdescribed herein. An aggregator entity may provide an arbitrageopportunity for a rewards program provider to lower the average cost ofredemptions. For example, a credit account provider may operate afrequent flyer miles rewards program. If a customer chooses to redeemhis or her miles with the credit account provider for a free airlineticket, the average cost to the provider may be 80 basis points (i.e.,0.8% of the accumulating transaction amount). If, however, the customerredeemed the same miles for cash, the cost to the provider may be only50 basis points. The credit account provider may therefore pay theaggregator (or any other entity offering the customer a choice betweenrewards programs) 60 basis points to help move the average cost awayfrom 80 basis points. The aggregator may then even pay the merchant 2basis points as an incentive and keep the 8 basis points difference asprofit. The aggregator may also make money by charging a subscriptionfee to customers using the service (e.g., upfront, based on usage, atend of year), charging customers a fee for converting rewards points tocash, or “rounding up” rewards points redemptions (e.g., 37,892 pointsto 38,000 points) and keeping the difference as a usage fee. It will berecognized that any computer system involved in rewards pointsredemption, not just the aggregator computer system described herein,may perform any of the actions above as well.

In various exemplary embodiments, a merchant computer system may alsoutilize existing communications mechanisms and processes used in theprocess of card transaction authorization and settlement to perform apurchase transaction using rewards points. It will be recognized bythose skilled in the art that in at least some exemplary financialtransactions (e.g., credit card transactions), there may be at least twophases: authorization and settlement. In the authorization phase, amerchant may perform various actions to find out whether a customer'sdesired transaction is valid (e.g., if the customer has sufficient fundsin his or her account or sufficient credit available to make aparticular purchase). If the transaction is valid, the merchant mayreceive payment for the transaction in the settlement phase (e.g., fromthe customer's account provider).

In reference to FIG. 6, account provider computer system 123 may beassociated with an account provider that provides an account to acustomer. The account provider may also offer a rewards programassociated with the account (e.g., offering points for purchases madeusing the account). Account provider computer system 123 may storeaccount information and rewards information in storage mechanism 125, asdescribed herein. Merchant computer system 102 may receive a purchaserequest comprising an account identifier for an account with the accountprovider. Merchant computer system 102 may then begin the process ofattempting to authorize the desired transaction by providing anauthorization request to merchant processor computer system 128. Theauthorization request may include, for example, information associatedwith the amount of the desired transaction, the account identifier usedfor the transaction (e.g., credit card number including a BIN),information associated with the requesting merchant, informationassociated with the product(s) or service(s) being purchased (e.g.,product names or identifiers), and/or any other information associatedwith the customer, the merchant, or the transaction. In variousexemplary embodiments, merchant computer system 102 may transmit theauthorization request to merchant processor computer system 128electronically over one or more networks, including network 106.

In various exemplary embodiments, merchant processor computer system 128may have a predefined relationship, agreement, or arrangement with themerchant associated with merchant computer system 102 to authorize andsettle card transactions on behalf of the merchant. Merchant processorcomputer system 128 may process transactions for a plurality ofmerchants and a plurality of customers. For example, TSYS AcquiringSolutions, LLC (TSYS), which those skilled in the art will recognize asan entity that authorizes and settles card transactions, may operate asthe merchant processor.

Merchant processor computer system 128 may provide the authorizationrequest, or any other authorization data, to card association computersystem 129 associated with the account identifier of the customer. Cardassociation computer system 129 may be associated with a cardassociation that administers cards and acts as a gateway between anaccount provider and a merchant from which a customer desires to make apurchase. Exemplary card associations may include, without limitation,Visa® and MasterCard®. For example, if the customer attempted to pay fora purchase with a Visa® cedit card, the authorization request may berouted to Visa®. If the customer attempted to pay for a purchase with aMasterCard® credit card, the authorization request may be routed toMasterCard®. Card association computer system 129 may perform variousactions to verify that the desired transaction may be completed andprovide the authorization request, or any other authorization data, toaccount provider computer system 123, which issued the customer's card.For example, if the customer obtained his or her card from a bank, thatbank may act as the account provider. Account provider computer system123 may perform various actions to verify that the desired transactionmay be completed and may also determine that the customer has rewardspoints available in one or more associated rewards programs. If thecustomer's account does not have an associated rewards program, accountprovider computer system 123 may create a well-known authorizationmessage approving or denying the transaction, which may be routedthrough card association computer system 129, merchant processorcomputer system 128, and network 106 to merchant computer system 102. Itwill be understood by those of ordinary skill in the art that themerchant may then complete the transaction with the customer and performsettlement in a similar manner to receive payment for the transactionfrom the account provider (e.g., weekly batch files for processing,electronic ACH transfers).

If, however, the customer's account has an associated rewards programwith rewards points available, account provider computer system 123 mayprovide a different message with rewards information to be routed to themerchant through the other components depicted in FIG. 6. For example,the message may comprise the name of the customer's rewards program, thename of the rewards program provider, the number of points accumulated,the cash value equivalent of those points, a conversion ratio forconverting between rewards points and cash, and any other informationassociated with the rewards program or accumulated rewards points.Merchant computer system 102 may then, as described herein, use thereceived information to provide the customer with the option to pay forhis or her desired purchase with rewards points or the provided accountor both. Communication between merchant computer system 102 and accountprovider computer system 123 may follow a similar path after thecustomer has made a selection so that the account provider can reducethe customer's rewards points accordingly and pay the merchant for thecash value equivalent of any redeemed rewards points. Also,communication between merchant computer system 102 and account providercomputer system 123 may involve communication with card associationcomputer system 129 and/or merchant processor computer system 128 as intraditional authorization and settlement procedures, as describedherein.

It will be recognized that rewards information may be provided by anysystem with access to such information other than account providercomputer system 123, such as card association computer system 129 ormerchant processor computer system 128. Also, any system depicted inFIG. 6, for example, may provide the customer with the option to pay fora purchase with rewards points. Also, it will be understood thatalthough only one account provider computer system 123, card associationcomputer system 129, merchant processor computer system 128, andmerchant computer system 102 are depicted in FIG. 6, multiple entitiesof each may communicate in various exemplary embodiments. Also, anysystem or systems may be substituted in place of the various componentsdepicted in FIG. 6 to utilize other communications mechanisms,processes, and networks to perform a purchase transaction using rewardspoints. For example, merchant computer system 102 may communicate withother systems via a payment network operated by a wireless serviceprovider (e.g., rather than through merchant processor computer system128 and card association computer system 129).

It will be also recognized that various entities described in referenceto FIG. 6 may charge other entities a fee for using their services. Forexample, the merchant processor associated with merchant processorcomputer system 128 may charge the merchant associated with merchantcomputer system 102 a predetermined percentage for each transaction(e.g., 2%) processed and reduce the amount paid to the merchantaccordingly. The merchant processor may also, for example, pay the cardassociation and/or account provider for using their services (e.g., 1.4%interchange fee). Also, any other entities may charge a fee forcommunicating or routing funds through the charging entity via anetwork. It will also be recognized that communicating informationoutside the normal authorization and settlement network in the mannerdescribed in reference to FIGS. 1 through 5 may avoid at least some ofsuch fees, particularly interchange fees. Doing so may financiallybenefit customers attempting to redeem their rewards points andencourage more redemption purchases at merchants.

FIG. 17 depicts an exemplary flow chart 800 which illustrates anexemplary method for performing a purchase transaction using rewardspoints according to various embodiments of the disclosure. At block 801,a computer system, such as a merchant computer system, may receive apurchase request from a customer computer system. The purchase requestmay be associated with or comprise an account identifier. At block 802,the computer system may determine whether rewards information isavailable for the provided account by, for example, searching data in adatabase for the account identifier. If not, the computer system mayrequest rewards information from the rewards program provider (oranother entity with access to such information) at block 803. At block804, rewards information may be received. Once rewards information forthe provided account is available, the computer system may determine atblock 805 whether there is an associated rewards program with associatedrewards points that are redeemable for the desired purchase (e.g., ifthere are enough rewards points and no restrictions on redemption). Ifnot, the computer system may complete the transaction using the accountat block 806 as requested by the customer. If so, the computer systemmay at block 807 provide the option for the customer to pay for thepurchase with the account or with certain rewards points. At block 808,the computer system may receive a selection of one or more rewardsprograms, one or more accounts, or portions of both. If one or morerewards programs were selected, the computer system may at block 809notify the corresponding rewards program providers so that they candeduct the appropriate number of rewards points and pay the merchanttheir corresponding cash value, which may be received at block 810. Ifone or more accounts were selected, the computer system may at block 811complete the respective portion of the transaction using the account(e.g., according to well-known authorization and settlement proceduresfor card transactions).

FIG. 18 depicts an exemplary flow chart 820 which illustrates anexemplary method for performing a purchase transaction using rewardspoints according to various embodiments of the disclosure. At block 821,a computer system, such as a rewards program computer system or accountprovider computer system, may receive account information for a desiredpurchase, such as a credit card number. At block 822, the computersystem may determine whether the account has an associated rewardsprogram with redeemable rewards points. If so, the computer system mayat block 824 provide rewards information to the entity that provided theaccount information and then receive a selection for payment (e.g.,rewards points or account or both) at block 825 and provide payment tothe merchant at block 826 for any rewards points that the customer choseto use to pay for the purchase. If not, the computer system may at block823 notify the entity that provided the account information accordingly.

The present invention may build customer loyalty to rewards programproviders that allow rewards points to be easily redeemed using thesystems and methods described herein. For example, a customer who isallowed to easily use his or her rewards points to make a purchase froma merchant (even when they could not be otherwise redeemed with theprovider directly) may be more likely to conduct future transactionswith the provider and/or merchant. A merchant providing its customerswith the option to pay with rewards points or an account may also giveits customers a significant advantage over other merchants that do nothave the same functionality and thereby encourage its customers to makemore purchases, which may increase the merchant's business. The presentinvention also allows rewards points to be efficiently used becausesmall amounts or unwanted portions of rewards points may be redeemedjust like currency rather than going to waste.

The embodiments of the present invention are not to be limited in scopeby the specific embodiments described herein. For example, a rewardsprogram provider may be any entity with an associated computer system,including, for example, an account provider, card issuer, merchant, orindependent entity. Or, communication between the components describedherein may be by any communication mechanism and information may bestored in any type of electronic storage mechanism. Or, user interfacesmay be in any format. Or, the system for performing a purchasetransaction using rewards points may be a collection of more than onecomputer, each operating collectively as the system. Or, the system maybe completely automated such that performing a purchase transactionusing rewards points does not require interaction with an operator or auser.

Thus, such modifications are intended to fall within the scope of thefollowing appended claims. Further, although some of the embodiments ofthe present invention have been described herein in the context of aparticular implementation in a particular environment for a particularpurpose, those of ordinary skill in the art should recognize that itsusefulness is not limited thereto and that the embodiments of thepresent invention can be beneficially implemented in any number ofenvironments for any number of purposes. Accordingly, the claims setforth below should be construed in view of the full breadth and spiritof the embodiments of the present invention as disclosed herein. Whilethe foregoing description includes many details and specificities, it isto be understood that these have been included for purposes ofexplanation only, and are not to be interpreted as limitations of theinvention. Many modifications to the embodiments described above can bemade without departing from the spirit and scope of the invention.

1. (canceled)
 2. A system for performing a purchase transaction usingrewards points comprising: a request module operable to receive arequest to make a purchase, wherein the purchase is for a total purchaseamount; a determination module operable to determine based on accountinformation associated with a customer account that the customer accountis associated with a plurality of rewards accounts comprising a firstrewards account with associated first rewards points and a secondrewards account with associated second rewards points, wherein thecustomer account is associated with a customer; and a transaction moduleoperable to provide an option to pay for the purchase using one or morepayment types of at least one financial account associated with thecustomer, a first portion of the first rewards points, and a secondportion of the second rewards points respectively, the transactionmodule being configured to provide data to a user interface module, theprovided data comprising specific criteria for determining an allocationof points between the first portion of the first rewards points and thesecond portion of the second rewards points to be used for the purchase;the user interface module operable to generate an interactive userdisplay using the provided data from the transaction module and transmitthe interactive user display to a customer device associated with thecustomer and in response to a customer request to make the purchase, theinteractive user display being configured to automatically preselect, ina single display, the allocation of points to be used for the purchaseand automatically arrange the first portion and the second portion indescending order based on the determined allocation; the transactionmodule further configured to: receive, from the customer device, a firstselection of the first portion of the first rewards points and a secondselection of the second portion of the second rewards points to be usedfor the purchase; and update the available first rewards points based onthe first selection and the available second rewards points based on thesecond selection.
 3. The system of claim 2, wherein the accountinformation is received and stored prior to receiving the request, andthe account information comprises a multi-character identifierassociated with a credit or debit card.
 4. The system of claim 2,wherein the request comprises the account information.
 5. The system ofclaim 2, wherein the account information comprises a bank identificationnumber associated with an account provider.
 6. The system of claim 5,wherein the bank identification number comprises the first sixcharacters of a credit or debit card number.
 7. The system of claim 2,wherein the determination module is operable to receive rewards programparticipation information.
 8. The system of claim 7, wherein the rewardsprogram participation information comprises an indication that thefinancial account is associated with the rewards program.
 9. The systemof claim 7, wherein the rewards program participation information isreceived from a rewards program provider associated with the rewardsprogram.
 10. The system of claim 9, wherein the rewards program provideris an account provider.
 11. The system of claim 7, wherein the rewardsprogram participation information is received from the customer.
 12. Thesystem of claim 7, wherein the rewards program participation informationis received in a batch file.
 13. The system of claim 2, wherein thedetermination module is operable to receive rewards information.
 14. Thesystem of claim 13, wherein the rewards information comprises anindication of an amount of associated first rewards points, an amount ofassociated second rewards points, an indication of the amount ofassociated first rewards points corresponding to the total purchaseamount, and an indication of the amount of associated second rewardspoints corresponding to the total purchase amount.
 15. The system ofclaim 13, wherein the rewards information comprises an indication of anamount of associated first rewards points, an amount of associatedsecond rewards points, and a conversion ratio for converting the firstrewards points and the second rewards points to their cash equivalent.16. The system of claim 13, wherein the rewards information is receivedfrom a rewards program provider associated with the rewards program. 17.The system of claim 16, wherein the rewards program provider is anaccount provider.
 18. The system of claim 2, wherein the customer makesthe purchase using a single card configured to provide payment using oneor more payment types of the financial account, the first portion of thefirst rewards points, and the second portion of the second rewardspoints, wherein the first rewards points and second rewards points areeach associated with a different merchant.
 19. The system of claim 13,wherein the rewards information is received in a batch file.
 20. Amethod for performing a purchase transaction using rewards pointscomprising: receiving, by a request module, a customer request to make apurchase by a customer in a single card transaction with a single card;determining, via a determination module, that a financial account of thecustomer is associated with a plurality of rewards accounts comprising afirst rewards account with associated first rewards points and a secondrewards account with associated second rewards points; providing data,via a transaction module, to a user interface module, the provided datacomprising specific criteria for determining an allocation of pointsbetween the first portion of the first rewards points and the secondportion of the second rewards points to be used for the purchase;generating, via the user interface module, an interactive user displayusing the provided data from the transaction module and transmitting theinteractive user display to a customer device associated with thecustomer and in response to the customer request to make the purchasewith the single card configured to provide payment using one or morepayments types of the financial account, a first portion of firstrewards points, and a second portion of second rewards points, theinteractive user display being configured to automatically preselect, ina single display, the allocation of points to be used for the purchaseand automatically arrange the first portion and the second portion indescending order based on the determined allocation; receiving, from thecustomer device, a first selection of the first portion of the firstrewards points and a second selection of the second portion of thesecond rewards points to be used for the purchase with the single card;and updating the available first rewards points based on the firstselection and the available second rewards points based on the secondselection.
 21. A system for performing a purchase transaction usingrewards points comprising: a request module operable to receive arequest to make a purchase, wherein the purchase is for a total purchaseamount; a determination module operable to determine based on accountinformation associated with a financial account that the financialaccount is associated with a plurality of rewards accounts comprising afirst rewards account with associated first rewards points and a secondrewards account with associated second rewards points, wherein thefinancial account is associated with a customer; and a transactionmodule operable to provide an option to pay for the purchase using oneor more payment types of the financial account, a first portion of thefirst rewards points, and a second portion of the second rewards pointsrespectively, the transaction module being configured to provide data toa user interface module, the provided data comprising specific criteriafor determining an allocation of points between the first portion of thefirst rewards points and the second portion of the second rewards pointsto be used for the purchase; the user interface module operable togenerate an interactive user display using the provided data from thetransaction module and transmit the interactive user display to acustomer device associated with the customer and in response to acustomer request to make the purchase with a single card in a singlecard transaction, the single card configured to provide payment usingone or more payment types of the financial account, the first portion ofthe first rewards points, and the second portion of the second rewardspoints, the interactive user display being configured to automaticallypreselect, in a single display, the allocation of points to be used forthe purchase and automatically arrange the first portion and the secondportion in descending order based on the determined allocation; thetransaction module further configured to: receive, from the customerdevice, a first selection of the first portion of the first rewardspoints and a second selection of the second portion of the secondrewards points to be used for the purchase with the single card in thesingle card transaction; and update the available first rewards pointsbased on the first selection and the available second rewards pointsbased on the second selection.